May it be a good idea to add ListView or even a DataGrid in the PopUp? ListView would add the possibility to have a more unfriendly PopUp and DataGrid would allow to add your own Items to the ItemSource.

I don't think there is any need for those right now, but they can always be added later. RN I would go with your current implementation and see how well it works out.

@timunie TBH what I need is a tool where I can put a list of all choices and get out a list of the ones user ticked. As long as that can be done I am fine with whatever way you achieved it.

Hi @Luk164 , @punker76 , @ExLuzZziVo and anyone else interested:

For my usecase I am now quite happy with the control. I would be very happy to get your feedback as well. You can try the control if you clone my branch and run the DemoApp.

@punker76 I will update the Codacy-issues later. Also I want to wait until #4009 from @batzen is merged.

Happy coding and a great weekend all of you
Tim

There is a new issue which we should remember to add to the documentation: timunie/TimsWpfControls#14 (comment)

Thank you @GWawrzeniecki for finding this.

@punker76 maybe you have an idea if we can load to the Popup before it is actually opened?

Instead of having the MultiSelectionComboBox.StringToObjectParser DependencyProperty, wouldn't it be better to make the conversion (MultiSelectionComboBox.cs:723) through the default TypeConverter for the good object type?

Hi @nalka0

thank you for this idea. At the moment I think I'll stick with the current implementation as it seems like this involves Reflexion which I try to avoid for performance reasons. Having the interface IParseStringToObject seems to be easy enough to implement.

Would it be an alternative for you if there is a build in StringToObjectParser which then may use the TypeConverter to provide the needed value?

Happy coding
Tim

Even though I don't think any user would notice some more milliseconds during the conversion of the new item he typed (so the performance aspect of this code is kind of irrelevant IMHO), using this implementation would also allow removing the StringToObjectParser dependency property and thus removing some Reflection (one less Binding).

Anyways, my approach here is to make the MSC (MultiSelectionComboBox) lighter for the developper who'll use it and to do things using the standard ways in order to reduce their code duplication. It may not be the best example but imagine someone wants to use your MSC with some System.Windows.Media.Brush, they would have to more or less copy what's in System.Windows.Media.BrushConverter.ConvertFrom(ITypeDescriptorContext, CultureInfo, object) and paste it in an IParseStringToObject implementation.

You proposed providing a built-in IParseStringToObject to wrap the TypeConverter, if you're going to stick with your implementation it looks like a good idea to me. Still, for all the reasons detailed above, I think always using the TypeConverter is better.

PS : I'm not that familiar with Github, are we in the good place to discuss this?

@timunie Wow, you did quite some work on this. I really hope this gets released soon.

Below is a list of still open points

• add AddingItemEvent
• add AddedItemEvent
• reset text only if Textbox does not have Keyboard focus as this may irritate the user
• check if we need the binding helper
• Add Control over ▲ and ▼-Keys. Currently they select the next element which is not good in Multiselection mode.

@punker76 I could need some help / guide regarding these issues

• Is there a way to use Binding to the IsSelected Property of the ListBoxItems? Seems like it is not triggered when drop-down is not open yet
• Is there a way to bind to SelectedItems via the Helper which we already have? I was not able to get this to work yet.

I played around with the control and have some feedback:

• First of all: Excellent work! 👍
• For my use case an option to add an "Select All" element would be really helpful.
  The Extended WPF Toolkit has a similiar control and has two properties for that IsSelectAllActive and SelectAllContent (see wiki page)
• How can I get the following behavior?
  • Result should look like Text -> switch IsEditable to On
  • User is not able to edit by entering characters -> switch IsReadOnly to On
  • User clicks on ComboBox and Dropdown should open (just like when IsEditable is Off) -> How? It only opens by clicking the arrow.

Hi @FroggieFrog

thank you for your feedback. Below please find some thoughts from my side:

For my use case an option to add an "Select All" element would be really helpful. [...]

Yes, I was also thinking of an option like this, but I want more. Maybe filtering, sorting, select all, select none, invert selection, add new item, what ever you can think of. So my idea is to add two ContentControls in the PopUp like this:

Then you can apply your style, your controls and your functions you like. Should not be too hard I guess. Let me know if this is a way for you as well.

How can I get the following behavior? [...] User clicks on ComboBox and Dropdown should open (just like when IsEditable is Off) -> How? It only opens by clicking the arrow.

I think this is not how a normal ComboBox works, so the MultiSelectionComboBox does not (try it in the Demo with a normal ComboBox). If the control is ReadOnly="True" and IsEditable="True" the use must still be able to select and copy the Text. If I capture the MouseDownEvent here to open the control this functionality is lost. So I think if you really need this, you will have to get the TextBox in code behind and listen to the PreviewMouseDown-Event as well as the GotFocus-Event.

// THE FOLLOWING CODE IS NOT PRODUCTION READY AND SHOULD ONLY SHOW THE BASIC CONECPT.
// Register to the loaded event of your MSCB
private void mscb_Example_Loaded(object sender, System.Windows.RoutedEventArgs e)
{
    if (sender is MultiSelectionComboBox multiSelectionComboBox)
    {
        multiSelectionComboBox.ApplyTemplate(); // Make sure the Template is loaded.
        if (multiSelectionComboBox.FindChild<TextBox>("PART_EditableTextBox") is TextBox textBox) // Get the TextBox
        {
            textBox.GotFocus -= TextBox_GotFocus; 
            textBox.GotFocus += TextBox_GotFocus; 
        }
    }
}

// Do the opening here.
private void TextBox_GotFocus(object sender, System.Windows.RoutedEventArgs e)
{
    if (mscb_Example.IsReadOnly && mscb_Example.IsEditable)
    {
        mscb_Example.SetCurrentValue(ComboBox.IsDropDownOpenProperty, true);
        e.Handled = true;
    }
}

Happy coding
Tim

@timunie your changes have been merged, thanks for your contribution 👍